Skip to content

fix: prevent session destruction during possession/unpossession#21

Open
insign wants to merge 1 commit into
mainfrom
fix-session-flush-on-possession-7268989724627422350
Open

fix: prevent session destruction during possession/unpossession#21
insign wants to merge 1 commit into
mainfrom
fix-session-flush-on-possession-7268989724627422350

Conversation

@insign

@insign insign commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Remove aggressive session flushing during possess and unpossess.

This PR removes Session::invalidate(), Session::regenerateToken(), and Session::flush() from logoutAndDestroySession because these methods unnecessarily wipe the entire session, destroying application states (such as shopping carts, checkout steps, or form data) when an admin impersonates or stops impersonating a user.

By removing these, the original session integrity is preserved while safely logging out the previous guard context.

Includes new test cases in tests/SessionFlushTest.php to ensure unrelated session data is safely retained across the actions.


PR created automatically by Jules for task 7268989724627422350 started by @insign

…mpersonation

Removes `Session::invalidate()`, `Session::regenerateToken()`, and `Session::flush()` from `logoutAndDestroySession` in `PossessionManager`. These methods were aggressively destroying all application session state (like shopping carts) instead of just managing the authentication status. This ensures standard application states remain intact while using the impersonation feature.

Co-authored-by: insign <1113045+insign@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant